> Yes, NaN values may still be used in any following floating point
> operations and the result will then be NaN whatever the operation
> and the other operands (except for tests). I think there is a way to
> cause a program to fail in this case, but I can't remember what it
> is (and it might require a modification of the source code).

Hm. Since the results will always be NaN, but tests return something
specific, maybe I could construct a validity-check which covers that exact
problem. Any ideas what tests I could do to find if it's a NaN? Obviously I
can't check if the value is equal to every known float, but if the value is
larger as well as smaller than a given other value, it surely has to be NaN
(I'm guessing that a test will always return false or true when coupled with
an NaN, so maybe checking to paradox things could be the clue).

Of course, to actually test any of this, I'd need a fail-proof way to
generate NaN. I might have to fumble a little with vaxis_rotate and the
<0,0,0>-axis...

Regards,
Tim

-- 
aka "Tim Nikias v2.0"
Homepage: <http://www.nolights.de>

Post a reply to this message